Design Round 6 · Deliverable 5 · The Create-from-Within cut · renders spec v5.2 · July 10, 2026

The cut — the smallest thing that can create

Every screen of R6 (and the adopted R5 flows), marked in or out for August 10 (5a) — and the one page that states the minimum coherent slice and its test (5b). The test is recursion: the invited can immediately invite, and the system that greeted them greets the next person better because they're in it now.

Every screen, marked

in — August 10

Ki's first session · ally creation as conversation01 · 1a

Profiler intake + input list restatement01 · 1b

Profile card (front/back) + code extension signature01 · 1c

The personal invitation page, pre-account01 · 1d

R5 onboarding + three-path $100 step, adoptedR5 · 01

First Chat mid-conversation + relationship card01 · 1e

Chat ⇄ Live switch + first Live arrival01 · 1f

Studio, the three-job cut + one package handoff01 · 1g

kiduna.live front door + arrival02 · 2a

Live HUD (four elements) + proximity actions02 · 2b–2c

Kidunaversity as sim-flagged Move (scoring grammar)02 · 2d

Tile/sprite/event set (closed) + generative fallback02 · 2e–2f

kiduna.one — front door + first minute03 · 3a

kiduna.live as product + the standing door03 · 3b–3c

/handle pages — member + ally, three distances04 · 4a–4c

out — created from within, after

The full Studio (R5 canvas 03: back-channel view, tool room, co-editing, MCP scoping)R5 · 03

The protocol browser and public metrics on kidunaverse.comR5 · 04

Kiduna Express — the whole surfaceR5 · 05

Authored art beyond Kidunaversity + the Club's Commons — the fallback carries the rest02 · 2f

Moves beyond Kidunaversity and the Spec Walk draft—

Voice in Live (Chat voice ships; the band is text in Live at launch)flagged, OQ-4

Treasury, Forums, grants-of-work UIs beyond what the R3/R4 cards already give ChatR3–R4

Telegram/Bluesky channel presences (the one-presence router ships headless first)—

"View as" on /handle pages · ally pages for co-owned allies04

The minimum coherent slice — one page

A member, their ally, and the ability to bring one more person in well.

The slice, across Chat and Live: Ki, able to onboard, explain, personalize an ally, and greet every guest · Chat whole (R3/R4 grammar: cards, chips, citations, press-and-hold, the gold ceremony) · the Profiler, so every invitation is prepared, never broadcast · the invitation page and R5's onboarding with the three-path $100 step · Live as one real place (the Club's Commons), one sim Move (Kidunaversity), the closed tile/sprite/event set, and the generative fallback carrying everything unauthored · the mode products as thin openings of the same build · Studio at exactly three jobs with the package handoff proven once · /handle pages so every member and ally resolves to something honest.

The test is recursion, run concretely: Moto invites swyx before lunch. By afternoon swyx says "I want to invite Alessio" — and his ally already knows the Profiler, because every ally is Ki. Nothing new ships in between. And Ki greets Alessio better than it greeted swyx, because swyx's corrections to his own profile taught the intake what a well-prepared arrival reads like from inside. The system that greeted them can greet the next person better because they're in it now.

What the slice refuses: any screen that exists to demonstrate the future instead of performing the present. The cut holds if and only if every included screen is exercised by the Moto→swyx→next-person chain; everything else is created from within, in public, under Apache 2.0.